fix: the method of veryfing password during LUKS creation #1103
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
ah the |
|
Maybe it's because |
|
Also, is it possible to automatically test the function of checking if the password is identical? I know little programming so I don't know how to do it... |
Lassulus
reviewed
Aug 15, 2025
| @@ -143,19 +143,21 @@ in | |||
|
|
|||
| askPassword() { | |||
| if [ -z ''${IN_DISKO_TEST+x} ]; then | |||
| set +x | |||
| promptSecret "Enter password for ${config.device}: " password | |||
| promptSecret "Enter password for ${config.device} again to be safe: " password_check | |||
| export password | |||
| [ "$password" = "$password_check" ] | |||
There was a problem hiding this comment.
probably better to use exit 1 if the password don't match instead of setting the debug flags
|
should be fixed by #1105 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixed issue:
#1102